CVE-2026-55961
wolfSSL_PKCS7_verify() reports success for degenerate (certs-only) PKCS#7 with no signer
Description
wolfSSL_PKCS7_verify() returning success for a degenerate (certs-only) PKCS#7 object that contains no signer. Such an object has empty signerInfos, so the underlying signed-data verification succeeds without authenticating any content. The compatibility-layer verify path now rejects the object when no signer signature has actually been verified, so a PKCS#7 carrying no valid signature is no longer reported as verified. This is enforced regardless of the PKCS7_NOVERIFY flag, which only suppresses signer certificate chain validation and was never intended to waive the requirement that a signature exist. Only affects OpenSSL compatibility builds that call the PKCS7_verify() compatibility API on potentially degenerate PKCS#7 bundles.
INFO
Published Date :
June 25, 2026, 4:51 p.m.
Last Modified :
June 25, 2026, 4:51 p.m.
Remotely Exploit :
Yes !
Source :
wolfSSL
Affected Products
The following products are affected by CVE-2026-55961
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 4.0 | HIGH | 50d2cd11-d01a-48ed-9441-5bfce9d63b27 | ||||
| CVSS 4.0 | HIGH | [email protected] |
Solution
- Update wolfSSL library to the latest version.
- Ensure PKCS#7 objects contain valid signatures.
- Avoid using degenerate PKCS#7 objects.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-55961 vulnerability anywhere in the article.